Generic object models and business process (re)design.

This paper explores the capacities of generic object-relationship models in the context of business process modeling and business process re-engineering. The presentation is based on a framework for strategic business function typology. It is shown how generic models can be developed for each kind of business function within the typology. Business process re-engineering can be represented by transformations of business models, corresponding to shifts within the typology framework. Although the results of the paper are presented by means of one particular dialect of the object-relationship approach, the results remain valid for all object oriented approaches that make use of objects and relationships. This paper contributes to the further formalisation of business process modeling.Models; Model; Processes;

Existence dependency: conceptual modelling by contract.

In Object Orientation, the Generalisation/Specialisation hierarchy and the Whole/Part relationship are prevalent classification schemes for object types. This paper presents a new classification scheme for object types, called 'existence dependency'. Existence dependency captures some of the interesting semantics that are usually associated with the concept of aggregation (Part of relation). In fact, the semantics of existence dependency are hidden in the semantics of the Entity Relationship model, but have never been explicitly named. We will demonstrate how the explicit classification of object types according to the existence dependency relation allows for formal and automatic consistency between static and dynamic aspects of object types that goes far beyond mere syntactical consistency.Classification; Dependency; Model;

Business process management: a bird's-eye view and research agenda.

Processes; Management; Research;

Modeling the dialogue aspects of an information system.

In this paper we investigate techniques offered by current object-oriented development methods for the specification of the user-system dialogue aspect of a software system. Current development methods do not give very extensive guidelines on how to model this aspect and the available techniques need some refinement and elaboration to fit this particular task in the software specification process. The paper first compares a number of approaches. The common elements of these approaches are summarized and further developed into one comprehensive set of techniques that addresses the needs of functional requirements analysis.

Improving the reuse possibilities of the behavioral aspects of object-oriented domain models.

Reuse of domain models is often limited to the reuse of the structural aspects of the domain (e.g. by means of generic data models). In object-oriented models, reuse of dynamic aspects is achieved by reusing the methods of domain classes. Because in the object-oriented approach any behavior is attached to a class, it is impossible to reuse behavior without at the same time reusing the class. In addition, because of the message passing paradigm, object interaction must be specified as a method attached to one class which is invoked by another class. In this way object interaction is hidden in the behavioral aspects of classes. This makes object interaction schemas difficult to reuse and customize. The focus of this paper is on improving the reuse of object-oriented domain models. This is achieved by centering the behavioral aspects around the concept of business events.Model; Models;

Domain modelling and the co-design of business rules in the telecommunication business area.

This paper discusses the development of an enterprise domain model in an environment where part of the domain knowledge is vague and not yet formalised in company-wide business rules. The domain model was developed for a young company starting in the telecommunications sector. The company relied on a number of stand-alone business support systems and sought for a manner to integrate them. There was opted for the development of an enterprise-wide domain model that had to serve as an integration layer to coordinate the stand-alone applications. A specific feature of the company was that it could build up its information infrastructure form scratch, so that many aspects of its business were still in the process of being defined. The paper will highlight parts of the Enterprise Model where there was a need for co-designing business rules together with the domain model. A result of this whole effort was that the company got more insight into important domain knowledge and developed a common understanding across functional areas of the way of doing business.domain modelling; business rules; object-oriented analysis; business process modelling;

Characterising aggregations with existence dependency.

Abstract: The concept of aggregation is considered as one of the basic principles in object-oriented analysis. There is however no standard definition of this concept and each object-oriented analysis method has its own definition of aggregation. The aim of this paper is not to discuss the different types of aggregation that exist. However, having assessed the complexity of the concept, we will illustrate how a basic set of formal concepts is sufficient to define of the structural and behavioral aspects of different existing flavours of aggregation. If a development method wants to offer a rich concept such as aggregation, it can define the semantics of the desired flavour of the aggregation using these core formal concepts. Analysts then have the choice to use the aggregation defined by the method or to fall back on the core concepts if a different flavour of aggregation is needed to model the situation at hand.Principles; Model;

Business process verification: a Petri Net approach.

In this report, we discuss the use of Petri Net language theory for business process modeling. Essentially, the focus is on the opportunities of the modeling technique for analysis and verification. Semantic compatibility, as opposed to syntactic compatibility, is concerned with the meaningfulness of the distributedbusiness process. We start with a description and motivation of different notions of semantically compatible business processes. Further, these different types ofcompatibility are formalized by means of Petri Net language theory. Finally, we describe the foundations of an algorithm that enables us to verify the semantic compatibility in an automated way.Keywords: Petri Net theory; Business Process Modeling; Verification; Semantic Com-patibilityBusiness process modeling; Petri Net theory; Semantic compatibility; Verification; Theory; Business; Processes; Process modeling; Opportunities;

Practical challenges for methods transforming i* goal models into business process models

The field of requirements engineering for business processes has grown during the last several years. As business processes are assumed to fulfil organizational goals, goal models could be transformed into business process models that specify how business processes fulfil the organizational goals. Although both the fields of Goal-Oriented RE (GORE) and Business Process Management (BPM) received a lot of attention from researchers, the methods to transform goal models into business process models still need further research. This paper analyses current methods to identify the practical challenges that need to be addressed for an effective transformation of goal models into business process models

Deterministic Petri net languages as business process specification language.

Today, a wide variety of techniques have been proposed to model the process aspects of business processes. The problem, however, is that many of these are focused on providing a clear graphical representation of the models and give almost no support for complex verification procedures. Alternatively, the use of Petri Nets as a business process modeling language has been repeatedly proposed. In complex business processes the use of Petri Nets has been criticized and the technique is believed to be unable to capture such processes in all aspects. Therefore, in this paper, we introduce the application of Petri Net language theory for business process specification. Petri Net languages are an extension to the Petri Net theory, and they provide a set of techniques to describe complex business processes more efficiently. More specifically, we advocate the application of deterministic Petri Net languages to model the control flow aspects of business processes. The balance between modeling power and analysis possibilities makes deterministic Petri Nets a highly efficient technique, used in a wide range of domains. The proof of their usability, as business process specification language, is given by providing suitable solutions to model the basic and more complex business process patterns [4]. Additionally, some points of particular interest are concisely discussed.Business; Business process modeling; Control; Model; Models; Patterns; Petri Net theory; Power; Process modeling; Processes; Representation; Theory; Verification;